Lawful intercept in future core interworking with evolved packet system

ABSTRACT

A method, a device, and a non-transitory storage medium are described in which a inter-networked lawful intercept service is provided. The inter-networked lawful intercept service may include providing lawful intercept information from a proxy call session control function to a future generation core network device. The proxy call session control function may be resident in an Internet Protocol Multimedia Subsystem network. The proxy call session control function may use a Diameter message that includes the lawful intercept information. The future generation core network device may be a policy control function. The lawful intercept information may be further provided to other core network devices, such as a session management function and a use plane function.

BACKGROUND

Development and design of new networks present certain challenges from anetwork-side perspective and an end device perspective. Typically, anetwork deployment supports lawful intercept of private communicationsby a law enforcement agency or other authorized entity. For example, inan evolved packet core (EPC) and Internet Protocol Multimedia Subsystem(IMS) network deployment, lawful intercept may be supported.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram illustrating an exemplary environment in which anexemplary embodiment of a inter-networked lawful intercept service maybe implemented;

FIG. 2 is a diagram illustrating another exemplary environment in whichan exemplary embodiment of a inter-networked lawful intercept servicemay be implemented;

FIGS. 3A-3I are diagrams illustrating an exemplary process of anexemplary embodiment of the inter-networked lawful intercept service;

FIG. 4 is a diagram illustrating exemplary components of a device thatmay correspond to one or more of the devices illustrated and describedherein;

FIG. 5 is a flow diagram illustrating an exemplary process of anexemplary embodiment of the inter-networked lawful intercept service;

FIG. 6 is a flow diagram illustrating another exemplary process of anexemplary embodiment of the inter-networked lawful intercept service;and

FIG. 7 is a flow diagram illustrating yet another exemplary process ofan exemplary embodiment of the inter-networked lawful intercept service.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

The following detailed description refers to the accompanying drawings.The same reference numbers in different drawings may identify the sameor similar elements. Also, the following detailed description does notlimit the invention.

Support for lawful intercept of a communication in a network is requiredin the United States and in some places abroad. With the development offuture networks, such as Fifth Generation (5G) networks and/or othertypes of new prospective networks, mechanisms that support lawfulintercept should be considered. However, in the design of a futurenetwork, there are considerations relating to inter-networking betweenthe future network, which includes various types of network devices, anda legacy network, which includes various legacy network devices.Furthermore, there are considerations relating to how such aninter-networking should be implemented. Additionally, in the context oflawful intercept, the inter-networking may not be limited to radioaccess networks and core networks, but may also include an applicationlayer network that provides a communication service to which the lawfulintercept may be directed.

According to exemplary embodiments, an inter-networked lawful interceptservice is described. According to an exemplary embodiment, theinter-networked lawful intercept service pertains to a 5G networkinter-networking with a Fourth Generation (4G) Evolved Packet System(EPS), such as an IMS network. According to other exemplary embodiments,the inter-networked lawful intercept service may pertain to another typeof EPS or non-future generation application service layer network. Forexample, the inter-networked lawful intercept service may pertain to anetwork other than the IMS network, such as a Rich Communication Service(RCS) network, or another type of application service layer network. Theapplication service layer network may support voice and/or other typesof communication services that may be subject to lawful intercept. Forexample, the other types of communication services may include SessionInitiation Protocol (SIP)-based communications, non-SIP-basedcommunication services (e.g., web browsing or other types of packet datatraffic), a video call, a Voice-over-Internet Protocol (VoIP) call, orother types of application services (e.g., Over-The-Top (OTT), RCS,etc.).

According to an exemplary embodiment of the inter-networked lawfulintercept service, a Call Session Control Function (CSCF) of an IMSnetwork may detect a communication setup for a user that is subject tolawful intercept surveillance. The Call Session Control Function maygenerate lawful intercept information that enables a requested lawfulintercept to be carried out. The Call Session Control Functioncommunicates the lawful intercept information to a network device of thefuture core network. For example, the future core network may beimplemented as a 5G core network. According to an exemplary embodiment,the network device of the 5G core network includes a Policy ControlFunction (PCF). According to another exemplary embodiment, the networkdevice of the future core network may be a non-standard core networkdevice, a proprietary core network device, or another type of corenetwork device.

According to some exemplary embodiments, the Call Session ControlFunction may communicate the lawful intercept information to the futurecore network via an intermediary network device. According to otherexemplary embodiments, the call session control function may communicatethe lawful intercept information to the future core network directlywithout the intermediary network device.

According to an exemplary embodiment of the inter-networked lawfulintercept service, the network device of the future core network mayprovide the lawful intercept information to other network devices of thefuture core network so that lawful intercept surveillance may beperformed. According to an exemplary embodiment, the PCF in the 5G corenetwork may pass the lawful intercept information to a SessionManagement Function (SMF), as described herein. Additionally, accordingto an exemplary embodiment, the SMF may provide lawful interceptinformation to a User Plane Function (UPF), as described herein.

In view of the foregoing, the inter-networked lawful intercept servicemay allow future network inter-networking with an IMS network in amanner that supports lawful intercept surveillance. For example, IMScommunication services via a 5G network may be subject to lawfulintercept. Given the transition from existing network architectures tofuture network architectures, the inter-networked lawful interceptservice may expand the use of network resources without forfeiting theiruse in existing frameworks.

FIG. 1 is a diagram illustrating an exemplary environment 100 in whichan exemplary embodiment of the inter-networked lawful intercept servicemay be implemented. As illustrated, environment 100 includes an accessnetwork 105 a core network 150, an external network 170, and a lawfulintercept (LI) network 180. Access network 105 includes access devices110, core network 150 includes core devices 155, external network 170includes external devices 175, and lawful intercept network 180 includeslawful intercept devices 185. Environment 100 further includes enddevices 199.

The number, type, and arrangement of networks illustrated in environment100 are exemplary. Additionally, or alternatively, other networks notillustrated in FIG. 1 may be included in environment 100, such as abackhaul/fronthaul network or another type of intermediary network, asdescribed herein.

The number, the type, and the arrangement of network devices in accessnetwork 105, core network 150, external network 170, as illustrated anddescribed, are exemplary. The number of end devices 199 is exemplary. Anetwork device, a network element, or a network function (referred toherein simply as a network device) may be implemented according to oneor multiple network architectures (e.g., a client device, a serverdevice, a peer device, a proxy device, a cloud device, a virtualizedfunction, and/or another type of network architecture (e.g., SoftwareDefined Networking (SDN), virtual, logical, network slicing, etc.)).Additionally, a network device may be implemented according to variouscomputing architectures, such as centralized, distributed, cloud (e.g.,elastic, public, private, etc.), edge, fog, and/or another type ofcomputing architecture.

Environment 100 includes communication links between the networks,between network devices, and between end device 199 and network devices.Environment 100 may be implemented to include wired, optical, and/orwireless communication links among the network devices and the networksillustrated. A communicative connection via a communication link may bedirect or indirect. For example, an indirect communicative connectionmay involve an intermediary device and/or an intermediary network notillustrated in FIG. 1. A direct communicative connection may not involvean intermediary device and/or an intermediary network. The number andthe arrangement of communication links illustrated in environment 100are exemplary.

Environment 100 may include various planes of communication including,for example, a control plane, a user plane, and a network managementplane. Environment 100 may include other types of planes ofcommunication. A message communicated in support of the inter-networkedlawful intercept service may use at least one of these planes ofcommunication. Additionally, an interface of a network device may bemodified (e.g., relative to an interface defined by a standards body,such as Third Generation Partnership Project (3GPP), InternationalTelecommunication Union (ITU), European Telecommunications StandardsInstitute (ETSI), etc.) or a new interface of the network device may beprovided in order to support the communication (e.g., transmission andreception of messages, Information Elements (IE), Attribute Value Pairs(AVPs), etc.) between network devices and the inter-networked lawfulintercept service logic, as described herein. According to variousexemplary implementations, the interface of the network device may be aservice-based interface or a reference point-based interface.

Access network 105 may include one or multiple networks of one ormultiple types and technologies. For example, access network 105 mayinclude a 4G RAN, a 4.5G RAN, a 5G RAN, and/or another type of futuregeneration RAN. By way of further example, access network 105 may beimplemented to include an Evolved UMTS Terrestrial Radio Access Network(E-UTRAN) of a Long Term Evolution (LTE) network, an LTE-Advanced(LTE-A) network, and/or an LTE-A Pro network, a next generation (NG)RAN, and/or another type of RAN (e.g., a legacy RAN). Access network 105may further include other types of wireless networks, such as a WiFinetwork, a Worldwide Interoperability for Microwave Access (WiMAX)network, a Local Area Network (LAN), a Bluetooth network, a PersonalArea Network (PAN), or another type of network (e.g., a legacy ThirdGeneration (3G) RAN, etc.) that may be considered a network edge.Additionally, or alternatively, access network 105 may include a wirednetwork, an optical network, or another type of network that may providean on-ramp to access devices 110 and/or core network 150.

According to various exemplary embodiments, access network 105 may beimplemented to include various architectures of wireless service, suchas, for example, macrocell, microcell, femtocell, picocell, metrocell,NR cell, LTE cell, non-cell, or another type of cell architecture.Additionally, according to various exemplary embodiments, access network105 may be implemented according to various wireless technologies (e.g.,radio access technologies (RATs), etc.), wireless standards, wirelessfrequencies/bands/carriers (e.g., centimeter (cm) wave, millimeter (mm)wave, below 6 Gigahertz (GHz), above 6 GHz, licensed radio spectrum,unlicensed radio spectrum, etc.), and/or other attributes of radiocommunication.

Access network 105 may include different and multiple functionalsplitting, such as options 1, 2, 3, 4, 5, 6, 7, or 8 that relate tocombinations of access network 105 and core network 150 including anEvolved Packet Core (EPC) network and/or a NG Core (NGC) network, or thesplitting of the various layers (e.g., physical layer, Media AccessControl (MAC) layer, Radio Link Control (RLC) layer, and Packet DataConvergence Control (PDCP) layer), plane splitting (e.g., user plane,control plane, etc.), Centralized Unit (CU) and Distributed Unit (DU),interface splitting (e.g., F1-U, F1-C, E1, Xn-C, Xn-U, X2-C, CommonPublic Radio Interface (CPRI), etc.) as well as other types of networkservices, such as Dual Connectivity (DC) or higher (e.g., a secondarycell group (SCG) split bearer service, a master cell group (MCG) splitbearer, an SCG bearer service, Non-StandAlone (NSA), StandAlone (SA),etc.), CA (e.g., intra-band, inter-band, contiguous, non-contiguous,etc.), network slicing, Coordinated MultiPoint (CoMP), various duplexschemes (e.g., Frequency Division Duplex (FDD), Time Division Duplex(TDD), Half-duplex FDD (H-FDD), etc.), and/or another type ofconnectivity service.

Depending on the implementation, access network 105 may include one ormultiple types of network devices, such as access devices 110. Forexample, access devices 110 may include an evolved Node B (eNB), a nextgeneration Node B (gNB), an evolved Long Term Evolution (eLTE) eNB, aRadio Network Controller (RNC), a Remote Radio Head (RRH), a BaseBandUnit (BBU), a CU, a DU, a small cell node (e.g., a picocell device, afemtocell device, a microcell device, a home eNB, etc.), a futuregeneration wireless access device, another type of wireless node (e.g.,a WiFi device, a WiMax device, a hotspot device, etc.) that provides awireless access service, or other another type of network device thatprovides a transport service (e.g., routing and forwarding), such as arouter, a switch, or another type of layer 3 (e.g., network layer of theOpen Systems Interconnection (OSI) model) network device. Access devices110 may include wired and/or optical devices (e.g., modem, wired accesspoint, optical access point, Ethernet device, etc.) that provide networkaccess.

Core network 150 may include one or multiple networks of one or multipletypes and technologies. According to an exemplary embodiment, corenetwork 150 includes a complementary network of access network 105. Forexample, core network 150 may be implemented to include an EPC of an LTEnetwork, an LTE-A network, an LTE-A Pro network, a next generation core(NGC) network, and/or a future generation network. Core network 150 mayinclude a legacy core network.

Depending on the implementation, core network 150 may include varioustypes of network devices, such as core devices 155. For example, coredevices 155 may include a Mobility Management Entity (MME), a PacketGateWay (PGW), a Serving GateWay (SGW), a Home Agent (HA), a GPRSSupport Node (GGSN), a Home Subscriber Server (HSS), an Authentication,Authorization, and Accounting (AAA) server, a Policy Charging and RulesFunction (PCRF), a Charging System (CS), a UPF, an Access and Mobilitymanagement Function (AMF), a SMF, a Unified Data Management (UDM)device, an AUthentication Server Function (AUSF), a Network SliceSelection Function (NSSF), a Network Repository Function (NRF), a PolicyControl Function (PCF), a NetWork Data Analytics Function (NWDAF), aNetwork Exposure Function (NEF), and/or an Application Function (AF).According to other exemplary implementations, core devices 155 mayinclude additional, different, and/or fewer network devices than thosedescribed. For example, core devices 155 may include a non-standardand/or a proprietary network device, or another type of network devicethat may be well-known but not particularly mentioned herein.

According to an exemplary embodiment, core devices 155 includes coredevice 155 that provides inter-networked lawful intercept service, asdescribed herein. For example, core device 155 may include PolicyControl Functions (e.g., a PCF) for a future core network (e.g., a 5Gcore network). Core device 155 may receive lawful intercept informationfrom external device 175, as described herein. Core device 155 mayreceive the lawful intercept information directly from external device175 or via an intermediary network device, as described herein. Coredevice 155 may provide the lawful intercept information to other coredevices 155 such that lawful intercept surveillance may be performed incore network 150. For example, the other core devices 155 may includeIntercept Access Point (IAP) logic that provides lawful interceptinformation, such as Intercept-Related Information (IRI) andCommunication Content (CC).

External network 170 may include one or multiple networks. For example,external network 170 may be implemented to include a service or anapplication-layer network, the Internet, the World Wide Web (WWW), anInternet Protocol Multimedia Subsystem (IMS) network, a RichCommunication Service (RCS) network, a cloud network, a packet-switchednetwork, a data center, an Intranet, a private network, a publicnetwork, or other type of network that hosts an end device applicationor service.

Depending on the implementation, external network 170 may includevarious network devices, such as external devices 175. For example,external devices 175 may provide various applications, services, orother type of end device assets, such as servers (e.g., web,application, cloud, etc.), mass storage devices, and/or data centerdevices. According to various exemplary implementations, the applicationservices may pertain to broadband services in dense areas (e.g.,pervasive video, smart office, operator cloud services, video/photosharing, etc.), broadband access everywhere (e.g., 50/100 Mbps, ultralow-cost network, etc.), higher user mobility (e.g., high speed train,remote computing, moving hot spots, etc.), Internet of Things (IoTs)(e.g., smart wearables, sensors, mobile video surveillance, smartcities, connected home, etc.), extreme real-time communications (e.g.,tactile Internet, augmented reality, etc.), lifeline communications(e.g., natural disaster, emergency response, etc.), ultra-reliablecommunications (e.g., automated traffic control and driving,collaborative robots, health-related services (e.g., monitoring, remotesurgery, etc.), drone delivery, public safety, etc.), broadcast-likeservices, real-time communications (e.g., voice, video conferencing,etc.), and/or messaging (e.g., texting, etc.).

External devices 175 may also include network devices that provide othernetwork-related functions, such as network management, load balancing,security, authentication and authorization, policy control, billing, androuting.

According to an exemplary embodiment, external devices 175 includeexternal device 175 that provides the inter-networked lawful interceptservice, as described herein. For example, external device 175 may be anetwork device of an IMS network. External device 175 may provide lawfulintercept information to core device 155 of a future core network (e.g.,core network 150) based on various triggering events, as describedherein. External device 175 may provide the lawful intercept informationto core device 155 directly or via an intermediary network device, asdescribed herein.

Lawful intercept network 180 includes a network that supports lawfulinterception. Lawful intercept network 180 may be accessed and used by aLaw Enforcement Agent (LEA) and other authorized entities. Lawfulintercept devices 185 may include various devices, such as anadministration function (ADMF), a Mediation Function (MF), a LawEnforcement Agency (LEA) device, and a Law Enforcement MonitoringFacility (LEMF) device. Lawful intercept network 180 may include variousLI interfaces (e.g., LI_ADMF, LI_X1, LI_X2, LI_X3, LI_HI1, LI_HI2,LI_HI3, etc.) that are used to communicate with, for example, corenetwork 150 and external network 170, and may be used to communicatecontent of communication (CC) and IRI information.

End device 199 includes a device that has computational andcommunicative capabilities (e.g., wired, wireless, optical, etc.).Depending on the implementation, end device 199 may be a mobile device,a portable device, a stationary device, a device operated by a user(e.g., User Equipment (UE), and so forth. For example, end device 199may be implemented as a smartphone, a mobile phone, a personal digitalassistant, a tablet, a netbook, a phablet, a wearable device (e.g., awatch, glasses, etc.), a computer, a device in a vehicle, or other typesof wireless, wired, and/or optical devices. End device 199 may beconfigured to execute various types of software (e.g., applications,programs, etc.). The number and the types of software may vary among enddevices 199.

End device 199 may support one or multiple RATs (e.g., 4G, 5G, etc.) andvarious portions of the radio spectrum (e.g., multiple frequency bands,multiple carrier frequencies, licensed, unlicensed, etc.), networkslicing, DC service, and/or other types of connectivity services.Additionally, end device 199 may include one or multiple communicationinterfaces that provide one or multiple (e.g., simultaneous) connectionsvia the same or different RATs, frequency bands, carriers, networkslices, and/or other communication medium (e.g., wired, etc.). Themultimode capabilities of end device 199 may vary among end devices 199.

FIG. 2 is a diagram illustrating an exemplary environment 200 in whichan exemplary embodiment of the inter-networked lawful intercept servicemay be implemented. As illustrated, environment 200 may include a 4G/5GRAN 205, a 4G/5G core network 215, and an IMS network 240. 4G/5G RAN 205may include an eNB 207 and a gNB 210. 4G/5G core network 215 may include4G core devices, such as a PCRF 217, an MME 220, a PGW 223, and an SGW225. Additionally, 4G/5G core network 215 may include 5G core devices,such as a PCF 230, an SMF/PGW-C 233, and a UPF/PGW-U 235. IMS network240 may include an Application Server (AS) 242, a Diameter Routing Agent(DRA) 250, and a Proxy-CSCF 245. Environment 200 may further include a5G-NSA device 260 and a 5G-SA device 265 (also referred to as end device260/265). Additionally, as further illustrated, environment 200 includesexemplary communication links between network devices and exemplaryinterfaces (e.g., Rx, N7, L1_T3/NF, Gx, S11, and S5/S8).

Similar to environment 100, the number, type, and arrangement ofnetworks in environment 200 are exemplary. Additionally, the number,type, and arrangement of network devices in 4G/5G RAN 205, 4G/5G corenetwork 215, and IMS network 240 are exemplary. Some network devices ofa network have been omitted from illustration for the sake of brevity.The number and the arrangement of communication links in environment 200are exemplary, as well as the interfaces. Environment 200 may alsoinclude various planes of communications, as described herein. Accordingto some exemplary embodiments, a network device may include a modifiedor a new interface to support a communication pertaining to theinter-networked lawful intercept service, as described herein.

eNB 207, gNB 210, PCRF 217, MME 220, PGW 223, and SGW 225 may eachoperate and provide functions according to a standard (e.g., 3GPP, ITU,etc.), a non-standard, and/or a proprietary technology. PGW 223 and SGW225 may each include logic that supports lawful interception andinterfaces with LI devices 185.

PCF 230 may operate and provide functions according a standard (e.g.,3GPP, ITU, etc.), a non-standard, and/or a proprietary technologyassociated with policy control functionalities, such as providing policyrules for control plane functions including network slicing, roaming,and mobility management, accessing subscription information relevant forpolicy decisions in a data repository (e.g., a UDM, a unified datarepository (UDR), etc.), and supporting 5G QoS policy and chargingcontrol functions.

According to an exemplary embodiment, PCF 230 may include logic thatprovides the inter-networked lawful intercept service, as describedherein. According to one exemplary embodiment as described herein, PCF230 may receive LI information from P-CSCF 245 via DRA 250 (or othersuitable intermediary network device). According to another exemplaryembodiment, as described herein, PCF 230 may receive LI information fromP-CSCF 245 directly (e.g., without an intermediary network device).According to one exemplary implementation, PCF 230 and P-CSCF 245 maydirectly communicate via an Rx interface. According to another exemplaryimplementation, PCF 230 and P-CSCF 245 may directly communication via aninterface other than an Rx interface (e.g., REST API, N5, etc.).

According to an exemplary embodiment, PCF 230 may include logic thatwhen a Diameter message or a message that includes lawful interceptinformation from P-CSCF 245 or DRA 250 is received, PCF 230 may forwardthe Diameter message or other type of message to SMF/PGW-C 233, asdescribed herein. For example, PCF 230 may forward the (Diameter)message to SMF/PGW-C 233 via an N7 interface.

SMF/PGW-C 233 may include a network device that may operate and providefunctions according to a standard (e.g., 3GPP, ITU, etc.), anon-standard, and/or a proprietary technology associated with SMF andPGW-C devices. For example, SMF/PGW-C 233 may include SMFfunctionalities, such as session management, UE IP address allocationand management, selection and control of a UPF, traffic steering, andcontrol part of policy enforcement and QoS at UPF/PGW-U 235. SMF/PGW-C233 may also include PGW functionalities that control the functionalityperformed by a PGW-U, such as selection and controls of the point ofattachment to that PDN for the life of the EPS bearer, resourcemanagement for bearer resources, bearer binding, subscriber IP addressmanagement, and mobility support. According to other exemplaryembodiments, SMF/PGW-C 233 may not include the functionalities relatingto a PGW-C. SMF/PGW-C 233 may include logic that supports lawfulinterception (e.g., IRI-Point Of Interception (IM-POI) logic,CC-triggering function logic (CC-TF, etc.), interfaces with LI devices185, as well as an LI interface with UPF/PGW-U 235 (e.g., LI_T3).

According to an exemplary embodiment, SMF/PGW-C 233 may include logicthat provides the inter-networked lawful intercept service, as describedherein. For example, SMF/PGW-C 233 may interpret and/or decode thelawful intercept information received from PCF 230. In response,SMF/PGW-C 233 may generate IRI pertaining to Packet Data Unit (PDU)session establishment, modification, and release based on the lawfulintercept information received from PCF 230. SMF/PGW-C 233 may alsogenerate IRI when a PDU session has already been established for atarget end device 260/265. Additionally, based on receiving the lawfulintercept information from PCF 230, SMF/PGW-C 233 may generate andtransmit a message to UPF/PGW-U 235 for CC interception. The message mayinclude lawful intercept parameters.

UPF/PGW-U 235 may include a network device that may operate and providefunctions according to a standard (e.g., 3GPP, ITU, etc.), anon-standard, and/or a proprietary technology associated with UPF andPGW-U devices. For example, UPF/PGW-U 235 may include UPFfunctionalities, such as packet routing and forwarding, packetinspection, policy rule enforcement on the user plane, traffic usagereporting, QoS handling on the user plane, and so forth. UPF/PGW-U 235may also include PGW user plane functionalities. According to otherexemplary embodiments, UPF/PGW-U 235 may not include the functionalitiesrelating to a PGW-U. UPF/PGW-U 235 may include logic that supportslawful interception (e.g., CC-POI logic), interfaces with LI devices185, as well as an LI interface with SMF/PGW-C 233 (e.g., LI_T3).UPF/PGW-U 235 may provide CC lawful interception based on the lawfulintercept parameters received from SMF/PGW-C 233.

AS 242 may include a network device that provides an end deviceapplication or service. AS 242 may operate in a service layer of IMSnetwork 240. For example, AS 242 may provide a voice service or anothertype of application or service (e.g., RCS) that may be subject to alawful interception.

P-CSCF 245 may operate and provide functions according to a standard(e.g., 3GPP, ITU, etc.), a non-standard, and/or a proprietarytechnology. For example, P-CSCF 245 may operate in a control layer ofIMS network 240. P-CSCF 245 may function as a SIP proxy that monitorssignaling between end device 260/265 and IMS network 240. For example,P-CSCF 245 may validate and forward requests from end device 260/265,and process and forward responses to end device 260/265. P-CSCF 245 maybe configured to provide other functions, such as a Policy DecisionFunction (PDF). P-CSCF 245 may include logic that supports lawfulinterception for communications supported by non-5G or future coredevices, interfaces with LI devices 185, and an interface to a 4G coredevice (e.g., PCRF, etc.) via which lawful intercept information may becommunicated.

According to an exemplary embodiment, P-CSCF 245 may include logic thatprovides the inter-networked lawful intercept service, as describedherein. P-CSCF 245 may be provisioned, by LI network 180, with lawfulintercept information. Generally, the lawful intercept information mayidentify the target of the lawful intercept and what action needs to betaken. According to various exemplary embodiments, the lawful interceptinformation may pertain to IRI or IRI and CC. The lawful interceptinformation may include intercept subject identifiers, IRI parametersand values, and CC parameters and values. As described herein, thelawful intercept information may pertain to various communications(e.g., voice, multimedia, packet data, etc.), SIP-based applications,and so forth. According to one exemplary embodiment, the lawfulintercept information may include information (e.g., AVPs, etc.), asdescribed in U.S. Pat. No. 8,588,109 B2, the disclosure of which isincorporated in its entirety herein. According to other exemplaryembodiments, the lawful intercept information may be according to astandard (e.g., 3GPP, ETSI, ITU, etc.), a non-standard, and/or aproprietary framework.

According to an exemplary embodiment, P-CSCF 245 may invoke theinter-networked lawful intercept service based on the detection of acommunication setup. According to other exemplary embodiments, P-CSCF245 may invoke the inter-networked lawful intercept service based onanother type of triggering event. For example, P-CSCF 245 may invoke theinter-networked lawful intercept service in response to a provisioningof lawful intercept information from LI network 180. P-CSCF 245 mayprovide lawful intercept information to PCF 230 regarding a target enddevice, which may be attached to IMS network 240, but a communicationsession has not been initiated, in response to a communication sessionthat is being set-up (e.g., triggered by a SIP INVITE message and thesession owner matches a target in an LI target database stored by theP-CSCF 245), an already existing communication session. According toother examples, P-CSCF 245 may provide lawful intercept information toPCF 230 when an IMS session (e.g., an IMS bearer) is being establishedfor all users. According to such an example, a third party monitoringmessage flows will not be able to detect which user session is undersurveillance, and this mechanism may satisfy the LI “undetectability” bythird party requirement.

According to some exemplary embodiments, the inter-networked lawfulintercept service may pertain to only a communication session that issupported (e.g., in whole or in part (e.g., dual connectivity, etc.) by5G core devices (e.g., UPF 235, SMF 233, etc.).

According to an exemplary embodiment, P-CSCF 245 may determine whetherto provide lawful intercept information to PCF 230 (directly orindirectly via DRA 250) or a 4G core device based on contextinformation, the lawful intercept information (e.g., intercept subjectidentifiers, etc.), and a communication setup message (e.g., a SIPmessage, etc.). For example, the context information may indicate thetype of target subscriber (e.g., 5G end device versus 4G end device),bearer setup information that may indicate use of 5G core networkdevices or not, and/or other types of information (e.g., target enddevice is attached and/or connected to a 5G core network, etc.).According to other exemplary embodiments, P-CSCF 245 may not make such adetermination. For example, P-CSCF 245 may provide lawful interceptinformation only to PCF 230 (and not 4G core devices).

As described, depending on the embodiment, P-CSCF 245 may transmitlawful intercept information to PCF 230, directly or indirectly via anintermediary network device (e.g., DRA 250). According to an exemplaryembodiment, P-CSCF 245 may include the lawful intercept information in aDiameter message. For example, the Diameter message may be anAuthentication Authorization Request (AAR) message or another type ofDiameter request message.

DRA 250 may include a network device that may route Diameter messagesbased on any field included in a Diameter message. DRA 250 may beconfigured to route a Diameter message (e.g., an AAR message, etc.)received from P-CSCF 245 to PCF 230. DRA 250 may also be configured toroute a message that includes lawful intercept information to PCF 230.

IMS network 240 may include other types of network devices, such as anInterrogating-CSCF (I-CSCF), a Serving-CSCF (S-CSCF), a Media ResourceFunction (MRF), a Domain Name System (DNS), a Session Border Controller(SBC), a Media GateWay (MGW), and other types of network devices whichhave been omitted from the Figures and description for the sake ofbrevity.

FIGS. 3A-3I are diagrams illustrating an exemplary process of theinter-networked lawful intercept service. Referring to FIG. 3A, P-CSCF245 may store lawful intercept information. For example, P-CSCF 245 mayhave received lawful intercept information from LI device 185. Accordingto an exemplary scenario, assume that the lawful intercept informationindicates that end device 260 is subject to lawful intercept.

Referring to FIG. 3B, assume that end device 260 registers with IMSnetwork 240. Thereafter, end device 260 initiates a SIP-basedcommunication. As a consequence, P-CSCF 245 may receive a SIP INVITEmessage, and may detect a communication setup 307. P-CSCF 245 maycompare a SIP header (e.g., a “P-Asserted-Identity” header, a “From”header, etc.) to the provisioned lawful intercept information. Accordingto this exemplary scenario, assume that P-CSCF 245 may determine thatthere is a match. According to some exemplary embodiments, P-CSCF 245may also access context information, and determine whether to transmitlawful intercept information to PCF 230 or not.

Referring to FIG. 3C, P-CSCF 245 may generate an intercept message 310.For example, based on the type of lawful interception, P-CSCF 245 maygenerate AVPs and/or other types of parameters and values that indicatethe subject of the lawful interception (e.g., subject identifier), theaction to be taken (IRI interception, CC interception, etc.), and otherinformation (e.g., an address/port for sending intercepted content,etc.). P-CSCF 245 may encrypt the message or a portion thereof.According to an exemplary implementation, P-CSCF 245 may include thelawful intercept information in a Diameter AAR message or other type ofDiameter request message.

Referring to FIG. 3D, P-CSCF 245 may transmit the message 315. Accordingto this exemplary scenario, P-CSCF 245 may transmit a message 320 to DRA250 via the Rx interface. DRA 250 may route the intercept message 325 toPCF 230 via the Rx interface. Referring to FIG. 3E, PCF 230 may receivemessage 320, and transmit the intercept message 330 to SMF/PGW-C 233 viaan N7 interface. For example, PCF 230 may be configured to forward anyAAR messages to SMF/PGW-C 233. Alternatively, PCF 230 may inspect theincoming message, determine that the message includes lawful interceptinformation, and forward the message to SMF/PGW-C 233.

Referring to FIG. 3F, SMF/PGW-C 233 may interpret the intercept message332. Based on the interpretation, SMF/PGW-C 233 may begin generating IRIpertaining to the PDU/IMS session. Referring to FIG. 3G, SMF/PGW-C 233may generate and transmit an intercept message 335 to UPF/PGW-U 235. Forexample, a message 340 may include lawful intercept informationpertaining to CC interception. Referring to FIG. 3H, UPF/PGW-U 235 mayreceive and interpret the intercept message 345. Based on theinterpretation, UPF/PGW-U 235 may begin generating CC information.Referring to FIG. 3I, SMF/PGW-C 233 and UPF/PGW-U 235 may provide an LIservice 350 associated with the IMS communication in which end device265 is target.

FIGS. 3A-3I illustrate an exemplary process of the inter-networkedlawful intercept service, according to other exemplary embodiments, theprocess may include additional, different, and/or fewer steps. Forexample, a triggering event for invoking the inter-networked lawfulintercept service, at P-CSCF 245, may be based on an event other than acommunication session setup (e.g., a voice call, etc.). For example, asdescribed herein, P-CSCF 245 may invoke the inter-networked lawfulintercept service based on various other events, such as theprovisioning of lawful intercept information by LI network 180, a loginor a registration process of end device 260/265 to IMS network 240,detection that an existing communication session of end device 260/265is subject to lawful surveillance, and/or some other circumstance thatrequires lawful interception information to be provided to PCF 230regarding a target end device 260/265.

FIG. 4 is a diagram illustrating exemplary components of a device 400that may be included in one or more of the devices described herein. Forexample, device 400 may correspond to access devices 110, core devices155, external devices 175, LI devices 185, end devices 199, PCF 230,SMF/PGW-C 233, UPF/PGW-U 235, P-CSCF 245, DRA 250, and other types ofnetwork devices, as described herein. As illustrated in FIG. 4, device400 includes a bus 405, a processor 410, a memory/storage 415 thatstores software 420, a communication interface 425, an input 430, and anoutput 435. According to other embodiments, device 400 may include fewercomponents, additional components, different components, and/or adifferent arrangement of components than those illustrated in FIG. 4 anddescribed herein.

Bus 405 includes a path that permits communication among the componentsof device 400. For example, bus 405 may include a system bus, an addressbus, a data bus, and/or a control bus. Bus 405 may also include busdrivers, bus arbiters, bus interfaces, clocks, and so forth.

Processor 410 includes one or multiple processors, microprocessors, dataprocessors, co-processors, graphics processing units (GPUs), applicationspecific integrated circuits (ASICs), controllers, programmable logicdevices, chipsets, field-programmable gate arrays (FPGAs), applicationspecific instruction-set processors (ASIPs), system-on-chips (SoCs),central processing units (CPUs) (e.g., one or multiple cores),microcontrollers, neural processing unit (NPUs), and/or some other typeof component that interprets and/or executes instructions and/or data.Processor 410 may be implemented as hardware (e.g., a microprocessor,etc.), a combination of hardware and software (e.g., a SoC, an ASIC,etc.), may include one or multiple memories (e.g., cache, etc.), etc.

Processor 410 may control the overall operation or a portion ofoperation(s) performed by device 400. Processor 410 may perform one ormultiple operations based on an operating system and/or variousapplications or computer programs (e.g., software 420). Processor 410may access instructions from memory/storage 415, from other componentsof device 400, and/or from a source external to device 400 (e.g., anetwork, another device, etc.). Processor 410 may perform an operationand/or a process based on various techniques including, for example,multithreading, parallel processing, pipelining, interleaving, etc.

Memory/storage 415 includes one or multiple memories and/or one ormultiple other types of storage mediums. For example, memory/storage 415may include one or multiple types of memories, such as, a Random AccessMemory (RAM), a Dynamic Random Access Memory (DRAM), a Static RandomAccess Memory (SRAM), a cache, a Read Only Memory (ROM), a ProgrammableRead Only Memory (PROM), an Erasable PROM (EPROM), an Electrically EPROM(EEPROM), a Single In-line Memory Module (SIMM), a Dual In-line MemoryModule (DIMM), a flash memory (e.g., 2D, 3D, NOR, NAND, etc.), a solidstate memory, and/or some other type of memory. Memory/storage 415 mayinclude a hard disk (e.g., a magnetic disk, an optical disk, amagneto-optic disk, a solid-state disk, etc.), a Micro-ElectromechanicalSystem (MEMS)-based storage medium, and/or a nanotechnology-basedstorage medium. Memory/storage 415 may include drives for reading fromand writing to the storage medium.

Memory/storage 415 may be external to and/or removable from device 400,such as, for example, a Universal Serial Bus (USB) memory stick, adongle, a hard disk, mass storage, off-line storage, or some other typeof storing medium (e.g., a Compact Disk (CD), a Digital Versatile Disk(DVD), a Blu-Ray Disk (BD), a Solid State Disk (SSD), etc.).Memory/storage 415 may store data, software, and/or instructions relatedto the operation of device 400.

Software 420 includes an application or a program that provides afunction and/or a process. As an example, with reference to P-CSCF 245,software 420 may include an application that, when executed by processor410, provides a function of the inter-networked lawful interceptservice, as described herein. Additionally, for example, with referenceto PCF 230, SMF/PGW-C 233, UPF/PGW-U 235, and DRA 250, software 420 mayinclude an application that, when executed by processor 410, provides afunction of the inter-networked lawful intercept service, as describedherein. Software 420 may also include firmware, middleware, microcode,hardware description language (HDL), and/or other form of instruction.Software 420 may also be virtualized. Software 420 may further includean operating system (OS) (e.g., Windows, Linux, Android, proprietary,etc.).

Communication interface 425 permits device 400 to communicate with otherdevices, networks, systems, and/or the like. Communication interface 425includes one or multiple wireless interfaces and/or wired interfaces.For example, communication interface 425 may include one or multipletransmitters and receivers, or transceivers. Communication interface 425may operate according to a protocol stack and a communication standard.Communication interface 425 may include an antenna. Communicationinterface 425 may include various processing logic or circuitry (e.g.,multiplexing/de-multiplexing, filtering, amplifying, converting, errorcorrection, application programming interface (API), etc.).Communication interface 425 may be implemented as a point-to-pointinterface, a service based interface, etc.

Input 430 permits an input into device 400. For example, input 430 mayinclude a keyboard, a mouse, a display, a touchscreen, a touchlessscreen, a button, a switch, an input port, speech recognition logic,and/or some other type of visual, auditory, tactile, etc., inputcomponent. Output 435 permits an output from device 400. For example,output 435 may include a speaker, a display, a touchscreen, a touchlessscreen, a light, an output port, and/or some other type of visual,auditory, tactile, etc., output component.

As previously described, a network device may be implemented accordingto various computing architectures (e.g., in a cloud, etc.) andaccording to various network architectures (e.g., a virtualizedfunction, etc.). Device 400 may be implemented in the same manner. Forexample, device 400 may be instantiated, created, deleted, or some otheroperational state during its life-cycle (e.g., refreshed, paused,suspended, rebooting, or another type of state or status), usingwell-known virtualization technologies (e.g., hypervisor, containerengine, virtual container, virtual machine, etc.) in a network.

Device 400 may perform a process and/or a function, as described herein,in response to processor 410 executing software 420 stored bymemory/storage 415. By way of example, instructions may be read intomemory/storage 415 from another memory/storage 415 (not shown) or readfrom another device (not shown) via communication interface 425. Theinstructions stored by memory/storage 415 cause processor 410 to performa process and/or a function, as described herein. Alternatively, forexample, according to other implementations, device 400 performs aprocess and/or a function as described herein based on the execution ofhardware (processor 410, etc.).

FIG. 5 is a flow diagram illustrating an exemplary process 500 of anexemplary embodiment of the inter-networked lawful intercept service.According to an exemplary embodiment, a P-CSCF may perform steps ofprocess 500. For example, according to an exemplary embodiment, P-CSCF245 of an IMS network 240 may perform the steps of process 500.According to an exemplary implementation, processor 410 executessoftware 420 to perform a step illustrated in FIG. 5, and describedherein. Alternatively, a step illustrated in FIG. 5 and describedherein, may be performed by execution of only hardware.

Referring to FIG. 5, in block 505, P-CSCF 245 may store lawful interceptinformation pertaining to a surveillance target. For example, the lawfulintercept information may include one or more subject identifiers thatare subject to lawful surveillance and action parameters and values(e.g., IRI parameters and values, CC parameters and values, etc.).

In block 510, P-CSCF 245 may detect a triggering event that invokes aninter-networked lawful intercept service. For example, P-CSCF 245 mayreceive a message that initiates a communication session. According toother examples, P-CSCF 245 may detect another type of event that invokesthe inter-networked lawful intercept service, as described herein.

In block 515, it may be determined whether to provide the lawfulintercept information to a PCF. For example, based on the detection ofthe triggering event, P-CSCF 245 may determine whether to provide thelawful intercept information to PCF 230. As previously described, P-CSCF245 may use context information, the lawful intercept information, andcommunication message information (e.g., a SIP header, etc.) todetermine whether lawful intercept information is to be providedregarding a target end device. P-CSCF 245 may make other determinations,such as whether the target end device is connected or attached to thenetwork (e.g., in whole or in part) via 5G core network devices.

When it is determined that P-CSCF 245 should provide the lawfulintercept information to PCF 230 (block 515-NO), then P-CSCF 245 doesnot provide the lawful intercept information to PCF 230 (block 520).According to some exemplary embodiments, process 500 may end. Accordingto other exemplary embodiments, P-CSCF 245 may provide the lawfulintercept information to another network device (e.g., PCRF 217).

When it is determined that P-CSCF 245 should provide the lawfulintercept information to PCF 230 (block 515-YES), P-CSCF 245 maytransmit the lawful intercept information to PCF 230. According tovarious exemplary embodiments, P-CSCF 245 may transmit the lawfulintercept information directly to PCF 230 or via an intermediary networkdevice (e.g., DRA 250). According to an exemplary embodiment, P-CSCF 245may transmit the lawful intercept information via an Rx interface.According to an exemplary embodiment, P-CSCF 245 may generate andtransmit a Diameter AAR message, which includes the lawful interceptinformation, to PCF 230. According to other exemplary embodiments, aspreviously described, other interfaces and/or messages may be used.

FIG. 5 illustrates an exemplary process 500 of the inter-networkedlawful intercept service, however, according to other embodiments,process 500 may include additional operations, fewer operations, and/ordifferent operations than those illustrated in FIG. 5, and describedherein. For example, P-CSCF 245 may determine that no lawful interceptinformation is to be provided to any other network device.

FIG. 6 is a flow diagram illustrating another exemplary process 600 ofan exemplary embodiment of the inter-networked lawful intercept service.According to an exemplary embodiment, a PCF may perform steps of process600. For example, according to an exemplary embodiment, PCF 230 of afuture generation network (e.g., 5G core network 215 or other type offuture generation core network) may perform the steps of process 600.According to an exemplary implementation, processor 410 executessoftware 420 to perform a step illustrated in FIG. 6, and describedherein. Alternatively, a step illustrated in FIG. 6 and describedherein, may be performed by execution of only hardware.

In block 605, a PCF may receive lawful intercept information from aP-CSCF. For example, PCF 230 may receive the lawful interceptinformation directly from P-CSCF 245 via an Rx interface (or otherinterface, as described herein) or via DRA 250 via an Rx interface.According to an exemplary embodiment, the lawful intercept informationmay be received in a Diameter AAR message or another type of requestmessage.

In block 610, the PCF may determine to forward the lawful interceptinformation to an SMF. For example, PCF 230 may determine to forward ortransmit the lawful intercept information to SMF 233 based on theinterface (e.g., Rx interface or other interface, as described herein)via which the message was received, detection that the message includeslawful intercept information, and/or the network device that sent themessage (e.g., DRA 250 or P-CSCF 245).

In block 615, the PCF may transmit the lawful intercept information tothe SMF. For example, PCF 230 may transmit the lawful interceptinformation to SMF 233 via an N7 interface or other type of interfacethat communicatively couples PCF 230 to SMF 233. According to anexemplary embodiment, PCF 230 may transmit a Diameter AAR message, whichincludes the lawful intercept information, to SMF 233. According toother exemplary embodiments, another type of Diameter request messagemay be used.

FIG. 6 illustrates an exemplary process 600 of the inter-networkedlawful intercept service, however, according to other embodiments,process 600 may include additional operations, fewer operations, and/ordifferent operations than those illustrated in FIG. 6, and describedherein.

FIG. 7 is a flow diagram illustrating yet another exemplary process 700of an exemplary embodiment of the inter-networked lawful interceptservice. According to an exemplary embodiment, an SMF may perform stepsof process 700. For example, according to an exemplary embodiment, SMF233 of a future generation network (e.g., 5G core network 215 or othertype of future generation core network) may perform the steps of process700. According to an exemplary implementation, processor 410 executessoftware 420 to perform a step illustrated in FIG. 7, and describedherein. Alternatively, a step illustrated in FIG. 7 and describedherein, may be performed by execution of only hardware.

In block 705, an SMF may receive lawful intercept information from aPCF. For example, SMF 233 may receive a Diameter AAR or other type ofDiameter request, which includes lawful intercept information, from PCF230. According to an exemplary embodiment, SMF 233 may receive thelawful intercept information via an N7 interface.

In block 710, the SMF may interpret the lawful intercept information.For example, SMF 233 may interpret the lawful intercept information,such as IRI information.

In block 715, the SMF may configure lawful interception for IRIpertaining to target. For example, SMF 233 may be configured tointercept IRI pertaining to a target end device (e.g., end device260/265.

In block 720, the SMF may generate a message that includes lawfulintercept CC information. For example, SMF 233 may generate a lawfulintercept message, which may be used by UPF 235 to conduct lawfulintercept of CC information, based on the lawful intercept informationreceived from PCF 230.

In block 725, the SMF may transmit the message to the UPF. For example,SMF 233 may transmit the message to UPF 235 via an L1-T3 interface or anN4 interface. SMF 233 may provide lawful interception pertaining to atarget end device based on the lawful interception information receivedfrom PCF 230.

FIG. 7 illustrates an exemplary process 700 of the inter-networkedlawful intercept service, however, according to other embodiments,process 700 may include additional operations, fewer operations, and/ordifferent operations than those illustrated in FIG. 7, and describedherein.

As set forth in this description and illustrated by the drawings,reference is made to “an exemplary embodiment,” “an embodiment,”“embodiments,” etc., which may include a particular feature, structureor characteristic in connection with an embodiment(s). However, the useof the phrase or term “an embodiment,” “embodiments,” etc., in variousplaces in the specification does not necessarily refer to allembodiments described, nor does it necessarily refer to the sameembodiment, nor are separate or alternative embodiments necessarilymutually exclusive of other embodiment(s). The same applies to the term“implementation,” “implementations,” etc.

The foregoing description of embodiments provides illustration, but isnot intended to be exhaustive or to limit the embodiments to the preciseform disclosed. Accordingly, modifications to the embodiments describedherein may be possible. For example, various modifications and changesmay be made thereto, and additional embodiments may be implemented,without departing from the broader scope of the invention as set forthin the claims that follow. The description and drawings are accordinglyto be regarded as illustrative rather than restrictive.

The terms “a,” “an,” and “the” are intended to be interpreted to includeone or more items. Further, the phrase “based on” is intended to beinterpreted as “based, at least in part, on,” unless explicitly statedotherwise. The term “and/or” is intended to be interpreted to includeany and all combinations of one or more of the associated items. Theword “exemplary” is used herein to mean “serving as an example.” Anyembodiment or implementation described as “exemplary” is not necessarilyto be construed as preferred or advantageous over other embodiments orimplementations.

In addition, while series of blocks have been described with regard tothe processes illustrated in FIGS. 5, 6, and 7, the order of the blocksmay be modified according to other embodiments. Further, non-dependentblocks may be performed in parallel. Additionally, other processesdescribed in this description may be modified and/or non-dependentoperations may be performed in parallel.

Embodiments described herein may be implemented in many different formsof software executed by hardware. For example, a process or a functionmay be implemented as “logic,” a “component,” or an “element.” Thelogic, the component, or the element, may include, for example, hardware(e.g., processor 410, etc.), or a combination of hardware and software(e.g., software 420).

Embodiments have been described without reference to the specificsoftware code because the software code can be designed to implement theembodiments based on the description herein and commercially availablesoftware design environments and/or languages. For example, varioustypes of programming languages including, for example, a compiledlanguage, an interpreted language, a declarative language, or aprocedural language may be implemented.

Use of ordinal terms such as “first,” “second,” “third,” etc., in theclaims to modify a claim element does not by itself connote anypriority, precedence, or order of one claim element over another, thetemporal order in which acts of a method are performed, the temporalorder in which instructions executed by a device are performed, etc.,but are used merely as labels to distinguish one claim element having acertain name from another element having a same name (but for use of theordinal term) to distinguish the claim elements.

Additionally, embodiments described herein may be implemented as anon-transitory computer-readable storage medium that stores data and/orinformation, such as instructions, program code, a data structure, aprogram module, an application, a script, or other known or conventionalform suitable for use in a computing environment. The program code,instructions, application, etc., is readable and executable by aprocessor (e.g., processor 410) of a device. A non-transitory storagemedium includes one or more of the storage mediums described in relationto memory/storage 415. The non-transitory computer-readable storagemedium may be implemented in a centralized, distributed, or logicaldivision that may include a single physical memory device or multiplephysical memory devices spread across one or multiple network devices.

To the extent the aforementioned embodiments collect, store or employpersonal information of individuals, it should be understood that suchinformation shall be collected, stored, and used in accordance with allapplicable laws concerning protection of personal information.Additionally, the collection, storage and use of such information can besubject to consent of the individual to such activity, for example,through well known “opt-in” or “opt-out” processes as can be appropriatefor the situation and type of information. Collection, storage and useof personal information can be in an appropriately secure mannerreflective of the type of information, for example, through variousencryption and anonymization techniques for particularly sensitiveinformation.

No element, act, or instruction set forth in this description should beconstrued as critical or essential to the embodiments described hereinunless explicitly indicated as such.

All structural and functional equivalents to the elements of the variousaspects set forth in this disclosure that are known or later come to beknown are expressly incorporated herein by reference and are intended tobe encompassed by the claims.

What is claimed is:
 1. A method comprising: storing, by a networkdevice, lawful intercept information pertaining to an end device thatwas received from a law enforcement agency, wherein the network deviceincludes a proxy-call session control function (P-CSCF) and is of anon-future generation application service layer network; detecting, bythe network device, a triggering event; determining, by the networkdevice in response to the detecting, whether to transmit the lawfulintercept information to a policy control function (PCF) of a futuregeneration core network based on context information pertaining to theend device; and transmitting, by the network device, the lawfulintercept information to the policy control function in response todetermining to transmit the lawful intercept information to the policycontrol function.
 2. The method of claim 1, wherein the proxy-callsession control function is included in an Internet Protocol MultimediaSubsystem (IMS) network.
 3. The method of claim 1, wherein thetransmitting comprises: transmitting, by the network device, the lawfulintercept information to the policy control function via an Rxinterface.
 4. The method of claim 3, wherein the transmitting furthercomprises: transmitting, by the network device, the lawful interceptinformation to the policy control function via a Diameter Routing Agentdevice.
 5. The method of claim 1, further comprising: generating, by thenetwork device, a Diameter Authentication Authorization Request (AAR)message that includes the lawful intercept information, and wherein thetransmitting further comprises: transmitting, by the network device, theAAR message to the policy control function.
 6. The method of claim 1,further comprising: determining, by the network device, that the enddevice is connected to the future generation core network based on thecontext information.
 7. The method of claim 1, wherein the detectingcomprises: receiving, by the network device, a Session InitiationProtocol Invite message that pertains to the end device.
 8. The methodof claim 1, further comprising: storing, by the network device, thecontext information pertaining to the end device; and comparing, by thenetwork device, the context information to the lawful interceptinformation.
 9. A network device comprising: a communication interface;a memory, wherein the memory stores instructions; and a processor,wherein the processor executes the instructions to: store lawfulintercept information pertaining to an end device that was received froma law enforcement agency, wherein the network device includes aproxy-call session control function (P-CSCF) and is of a non-futuregeneration application service layer network; detect a triggering event;determine, in response to the detection, whether to transmit the lawfulintercept information to a policy control function (PCF) of a futuregeneration core network based on context information pertaining to theend device; and transmit, via the communication interface, the lawfulintercept information to the policy control function in response todetermining to transmit the lawful intercept information to the policycontrol function.
 10. The network device of claim 9, wherein theproxy-call session control function is included in an Internet ProtocolMultimedia Subsystem (IMS) network.
 11. The network device of claim 9,wherein, when transmitting, the processor further executes theinstructions to: transmit, via the communication interface, the lawfulintercept information to the policy control function via an Rxinterface.
 12. The network device of claim 11, wherein, whentransmitting, the processor further executes the instructions to:transmit, via the communication interface, the lawful interceptinformation to the policy control function via a Diameter Routing Agentdevice.
 13. The network device of claim 9, wherein the processor furtherexecutes the instructions to: generate a Diameter AuthenticationAuthorization Request (AAR) message that includes the lawful interceptinformation, and wherein, when transmitting, the processor furtherexecutes the instructions to: transmit, via the communication interface,the AAR message to the policy control function.
 14. The network deviceof claim 9, wherein the processor further executes the instructions to:determine that the end device is connected to the future generation corenetwork based on the context information.
 15. The network device ofclaim 9, wherein the triggering event comprises: receive, via thecommunication interface, a Session Initiation Protocol Invite messagethat pertains to the end device.
 16. The network device of claim 9, theprocessor further executes the instructions to: store the contextinformation pertaining to the end device; and compare the contextinformation to the lawful intercept information.
 17. A non-transitorycomputer-readable storage medium storing instructions executable by aprocessor of a device, which when executed cause the device to: storelawful intercept information pertaining to an end device that wasreceived from a law enforcement agency, wherein the device includes aproxy-call session control function (P-CSCF) and is of a non-futuregeneration application service layer network; detect a triggering event;determine, in response to the detection, whether to transmit the lawfulintercept information to a policy control function (PCF) of a futuregeneration core network based on context information pertaining to theend device; and transmit the lawful intercept information to the policycontrol function in response to determining to transmit the lawfulintercept information to the policy control function.
 18. Thenon-transitory computer-readable storage medium of claim 17, wherein theproxy-call session control function is included in an Internet ProtocolMultimedia Subsystem (IMS) network.
 19. The non-transitorycomputer-readable storage medium of claim 18, wherein the instructionsto transmit further comprise instructions, which when executed cause thedevice to: transmit the lawful intercept information to the policycontrol function via an Rx interface.
 20. The non-transitorycomputer-readable storage medium of claim 17, wherein the instructionsto further comprise instructions, which when executed cause the deviceto: determine that the end device is connected to the future generationcore network based on the context information.